Skip to content

tesla: send OAuth token calls to fleet-auth host (0.4.1) - #122

Merged
hasaanhameed merged 1 commit into
mainfrom
tesla-fleet-auth-token-host
Nov 13, 2026
Merged

hasaanhameed merged 1 commit into
mainfrom
tesla-fleet-auth-token-host

Conversation

@hasaanhameed

Copy link
Copy Markdown
Contributor

Regenerates the Tesla plugin against the updated SDKs.

What changed

  • The spec's tokenUrl (authorization code and client credentials) now points to https://fleet-auth.prd.vn.cloud.tesla.com/oauth2/v3/token. Tesla's docs require all /token calls on that host.
  • The SDKs get a third server, accessTokenServer, for /token. /authorize stays on authServer (auth.tesla.com), API calls on default (fleet-api).
  • SDK commits: tesla-typescript-sdk 8248d7c, tesla-python-sdk 04c97ff, tesla-csharp-sdk 1b0e7db.
  • Skills updated to name the new token host and server; version bumped 0.4.0 → 0.4.1 in all manifests.

Verified

  • All three SDKs build (TS type-check, Python compileall, C# 0 errors).
  • Localhost test of the TS SDK: login page on auth.tesla.com, code exchange, refresh and partner token on fleet-auth, API calls on fleet-api.

Still open: Tesla also requires an audience form field on the client-credentials and authorization-code token calls, which the SDKs can't send yet (apimatic/codegen-v2#817).

🤖 Generated with Claude Code

The Tesla SDKs now send /token (authorization code exchange, refresh and
client credentials) to fleet-auth.prd.vn.cloud.tesla.com, as Tesla requires,
via a new accessTokenServer. /authorize stays on auth.tesla.com. Bumps the
plugin to 0.4.1.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@hasaanhameed
hasaanhameed merged commit 416c0ac into main Nov 13, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant